[WIP] test_reference_broken - #38

Coverage decreased (-15.9%) to 66.385% when pulling efdd67c on johnnychen94:broken into 46d650a on Evizero:master.

I wonder if we shoukld infact switch to having a function that returns true or false,
or throws an error, depending.

Then we could do:

@test matches_reference(actual, "reference.txt")
@test_broken matches_reference(actual, "reference.txt")
@test_skip matches_reference(actual, "reference.txt")
@test !matches_reference(actual, "reference.txt")

rather than having to recrate each.

Are we getting value out of having a top-level macro that we couldn't get out of a function?

I wonder if we shoukld infact switch to having a function that returns true or false,
or throws an error, depending.

I like this idea a lot; I've been continuing thinking of replacing @test_reference by test_reference these days.

So export test_reference and deprecate @test_reference?

yeah, i think so.
We might want to bike-shed on the name a bit first though.

@test test_reference(actual, "reference.txt")

to me doesn't feel right.

and

@test !test_reference(actual, "reference.txt")

feels really wrong. (It is a weird thing to do in the first place but anyway...)

Definately will want a deprecation this time.
Which means first tagging a nonbreaking relese with the deprecation
then a breaking release (at some point) with the deprecation removed.